Smart user input devices, and systems and methods for monitoring such smart user input devices

ABSTRACT

Implementations of the disclosure describe smart controls for video game controllers that may track and store information related to their use (e.g., actuations) over time to keep track of their expected remaining life. The smart controls may removably couple to a video game controller and be replaced by other smart controls. In implementations, a smart control may include: an actuation component; a sensor to detect actuation of the actuation component in response to movement of the control; a memory to store information associated with the detected actuation; and a casing to house the sensor and memory.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent Application.No. 62/506,808, filed May 16, 2017, which is incorporated herein byreference in its entirety.

TECHNICAL FIELD

The present disclosure relates generally to videogame controllers, andmore particularly some embodiments relate to systems and methods formonitoring and/or analyzing the lifetime of videogame controllercomponents such as user input devices.

BACKGROUND OF THE DISCLOSURE

Modern videogames have become increasingly complex, and so to have thecontrollers used to play them. Videogame controllers often include aplurality of buttons, paddles, thumb-sticks, joysticks, wheels, pads,triggers and/or dials that may be pressed, pulled, turned or otherwisemaneuvered by a user to activate various functions within the videogamebeing played. As these controls are maneuvered, electrical signals aregenerated and processed, and ultimately one or more data packets istransmitted (via signal) to the gaming console (e.g., Microsoft Xbox360®, Sony PS4®, Nintendo Wii®, and/or any other computing device,etc.). The console interprets the signals and effectuates the operationsor functionality within the videogame environment that correspond to thecontrols that were pressed or maneuvered by the user.

Because the controls include mechanical componentry, their structuraland mechanical features often wear down or wear out with time, andsometimes fail to perform their intended functionality. Thus, suchcontrols often need to be replaced. In many instances, a control'sfailure occurs during a game. That is, the failure is discovered as theuser attempts to activate certain functionality during a game, and thefunctionality fails to execute. Such failures can undermine the user'sperformance in that game, and in future games until they eitherreplace/repair the control, or switch to a different videogamecontroller with working controls.

SUMMARY

Implementations of the disclosure describe smart controls for video gamecontrollers that may track and store information related to their use(e.g., actuations) over time to keep track of their expected remaininglife. The smart controls may removably couple to a video game controllerand be replaced by other smart controls. In implementations, a smartcontrol may include: an actuation component; a sensor to detectactuation of the actuation component in response to movement of thecontrol; a memory to store information associated with the detectedactuation; and a casing to house the sensor and memory.

In one embodiment, a user input device includes: a structural interfacecomponent to coupled to an actuation component; and a sensor moduleincluding: the actuation component; a sensor to detect actuation of theactuation component in response to movement of the structural interfacecomponent; a memory to store information associated with the detectedactuation; and a casing to house the sensor and memory. Inimplementations, the user input device is a control of video gamecontroller. For example, the structural interface component of thecontrol may include a thumbstick, a directional pad, a button, atrigger, or a bumper.

In particular implementations, the structural interface component is athumbstick, the actuation component includes a rod, and the thumbstickis coupled to the rod such that when the thumbstick is moved in adirection, the sensor detects actuation of the rod.

In particular implementations, the structural interface component is adirectional pad, the actuation component includes tact buttons, and thedirectional pad is coupled to the tact buttons such that when thedirectional pad is pressed in an area over one of the tact buttons, thesensor detects actuation of the tact buttons.

In implementations, the user input device is to electrically andphysically couple to the video game controller, and a processor of thevideo game controller is to receive a signal generated by the sensor inresponse to detecting actuation. In response to receiving the signal,the processor of the video game controller may cause data to be storedin the memory. For example, the processor may update a stored count ofthe number of times the control has been actuated, update an estimate ofthe number of control actuations remaining until expected failure of thecontrol or a component thereof, or update some other parameter stored inthe memory that may be used to track the usage and/or life expectancy ofthe control.

In implementations, the user input device may include one or moreconducting pins to electrically couple the user input device to thevideo game controller such that the video game controller is to causedata corresponding to usage of the user input device to be written intothe memory.

In implementations, the user input device may include a light emittingdiode to provide a visual indication about a condition of the user inputdevice using at least the information stored in the memory.

In implementations, the memory may store a read-only identifier of theuser input device.

In implementations, the memory may store a value corresponding to atotal number of detected actuations of the control over a period of time(e.g., a count of actuations since the control was first used, since thecontrol was previously serviced, or during some other period) or a valuecorresponding to a total number of remaining actuations of the controlbefore expected failure. For example, a count of total detectedactuations stored in memory may be incremented each time the control isactuated.

In implementations, the memory may store a value representing a lifeexpectancy of the user input device or a subcomponent of the user inputdevice based on a total number of actuations of the control (e.g., totalnumber of actuations before expected failure). For example, an estimateof total remaining actuations before expected failure may be decrementedeach the time the control is actuated.

In implementations, the control is removably coupled to the video gamecontroller. For example, usage data stored in the memory of the controlmay be used to determine that it requires replacement. Thereafter, thecontrol may be uncoupled from the video game controller and replaced byanother control. In implementations, the structural interface componentto removably coupled to the actuation component.

In one embodiment, a video game controller includes: a control, thecontrol including: an actuation component; a sensor to detect actuationof the actuation component in response to movement of the control; amemory to store information associated with the detected actuation; anda casing to house the sensor and memory. In implementations, the controlelectrically and physically couples to the video game controller, andthe video game controller includes a processor configured to receive asignal generated by the sensor in response to detecting actuation, andthe processor causes data to be stored in the memory in response toreceiving the signal.

In some implementations, the video game controller may include aplurality of controls, each of the controls respectively including: anactuation component; a sensor to detect actuation in response tomovement of the control; a memory to store information associated withthe detected actuation; and a casing to house the control's sensor andmemory. Each of the plurality of controls may electrically andphysically couple to the video game controller. The memory of each ofthe plurality of controls may store a value corresponding to a totalnumber of detected actuations of the control over a period of time or avalue corresponding to a total number of remaining actuations of thecontrol before expected failure. Each of the plurality of controls maybe removably coupled to the video game controller.

In one embodiment, a method includes: detecting movement of a control ofa video game controller; storing a record of the occurrence of themovement in a memory of the control; computing a total usage measure forthe control using at least the stored record and prior detectedmovements of the control; and determining an expected life of thecontrol using at least the total usage measure. In implementations, themethod further includes: presenting a graphical user interface to auser, the graphical user interface displaying a visual representation ofthe determined expected life. In implementations, the method mayimplemented by using a processor to execute instructions stored in anon-transitory computer-readable medium. For example, the method may beimplemented by executing instructions stored in a storage of acontroller, a storage of a control, and/or a storage of a gamingconsole.

Other features and aspects of the disclosed technology will becomeapparent from the following detailed description, taken in conjunctionwith the accompanying drawings, which illustrate, by way of example, thefeatures in accordance with implementations of the disclosed technology.The summary is not intended to limit the scope of any inventionsdescribed herein, which are defined by the claims and equivalents.

It should be appreciated that all combinations of the foregoing concepts(provided such concepts are not mutually inconsistent) are contemplatedas being part of the inventive subject matter disclosed herein. Inparticular, all combinations of claimed subject matter appearing at theend of this disclosure are contemplated as being part of the inventivesubject matter disclosed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure, in accordance with one or more implementations,is described in detail with reference to the following figures. Thefigures are provided for purposes of illustration only and merely depictexample implementations. Furthermore, it should be noted that forclarity and ease of illustration, the elements in the figures have notnecessarily been drawn to scale.

Some of the figures included herein illustrate various implementationsof the disclosed technology from different viewing angles. Although theaccompanying descriptive text may refer to such views as “top,” “bottom”or “side” views, such references are merely descriptive and do not implyor require that the disclosed technology be implemented or used in aparticular spatial orientation unless explicitly stated otherwise.

FIG. 1 illustrates a top view of an example videogame controller withmultiple UIDs with which the technology described herein may beimplemented.

FIG. 2 illustrates several example SICs that may used in UIDs ofvideogame controllers, in accordance with one or more embodiments of thepresent disclosure.

FIG. 3 illustrates a perspective view of an example videogame controllerwhere the directional pad UID and joystick UIDs are shown as removedfrom their coupled positions with respect to the rest of the videogamecontroller, in accordance with one or more embodiments of the presentdisclosure.

FIG. 4 illustrates a partially exploded view of an example smart UID, inaccordance with one or more embodiments of the present disclosure.

FIG. 5 illustrates a partially exploded view of an example directionalpad styled smart UID, in accordance with one or more embodiments of thepresent disclosure.

FIG. 6 illustrates an example GUI that may be configured to provideabout one or more smart UIDs of a connected videogame controller, inaccordance with one or more embodiments of the present disclosure.

FIG. 7 illustrates an example system within which the smart UIDtechnology of the present disclosure may be implemented, in accordancewith one or more embodiments of the present disclosure.

FIG. 8 illustrates an example method for providing information to a userrelevant to a smart UID, in accordance with one or more embodiments ofthe present disclosure.

FIG. 9 illustrates an example method for providing information to a userrelevant to a smart UID, in accordance with one or more embodiments ofthe present disclosure.

FIG. 10 illustrates an example computing module that may be used, eitherin the smart UID, the video game controller, or the console of thepresent disclosure to implement various features of the systems andmethods as disclosed herein.

The figures are not exhaustive and do not limit the present disclosureto the precise form disclosed.

DETAILED DESCRIPTION

As noted above, modern videogame controllers include a plurality of userinput devices (“UIDs”) that a user can maneuver to effectuatefunctionality within a game. Examples of such UIDs include buttons,triggers, paddles, wheels, dials, thumb-sticks, joysticks, directionalpads, discs, etc., and related circuitry and componentry. Over time,these UIDs may begin to malfunction. For instance, with increased usage,the structural features of UIDs may begin to wear, become damaged,erode, attract dirt or other particulates that impede movement or otherfunctions, etc. As noted above, such failures may undermine a gamer'sperformance in the game and future games until the UID is replaced orrepaired, or until the controller is replaced.

In view of these drawbacks, there is a need in the art for a way topredict, estimate, or approximate when a control or other mechanicalpart of a videogame controller will fail, and/or a way to of inform auser of this information before the UID actually fails (so that the usermay acquire replacement parts to swap in for their soon-to-fail partsbefore they actually fail). To this end, the technology of the presentdisclosure addresses the foregoing drawbacks, and provides solutions toavoid such drawbacks. In accordance with some implementations, thepresent disclosure is directed toward “smart” UIDs (sometimes referredto as UIDs) that may track and store information related to their use(e.g., actuations) over time to keep track of their expected remaininglife.

In accordance with implementations, a smart UID may include a structuralinterface component (“SIC”) coupled to a sensor module component (“SMC”)that can be operatively (i.e., mechanically, electrically, and/orcommunicatively) coupled with a videogame controller or other device andits constituent parts (e.g., its housing, processing engine, memory,power source, etc.). The SMC may include an actuation component, asensor to detect actuation of the actuation component in response tomovement of the structural interface component; and a memory to storeinformation associated with the detected actuation. For example, thememory may store a total number of actuations of the smart UID over itslifetime, a number of actuations remaining before expected failure ofthe smart UID, and other information that tracks the use and/orcondition of the smart UID over its life.

In some implementations, a SIC of a smart UID may be removable and/orreplaceable. For example, SICs may be removably coupled to a SMC. Insome instances, an entire smart UID may be removable and/or replaceable(including the SIC and SMC associated therewith). Accordingly, a usermay keep track of a condition of each smart UID, remove all or part of aUID that has malfunctioned, and repair or replace one or more of itscomponents as needed.

FIG. 1 illustrates a top view of an example videogame controller withmultiple UIDs with which the technology described herein may beimplemented. As shown, videogame controller 10 includes triggers 12,bumpers 14, guide button 16, A/B/X/Y buttons 18, joysticks 20,back/start buttons 22, and a directional pad 24. For clarity andunderstanding, reference will be made throughout this disclosure to oneor more of the UID types referred to in FIG. 1. It should beappreciated, however, that the technology disclosed herein extends toany style of UID and/or any configuration or arrangement of multipleUIDs as may be desired. Furthermore, the present disclosure may also beapplied to other electronics other than videogame controllers that haveUIDs subject to failure with increased wear and tear as usage continues(e.g., remote control devices, keyboards and other computer peripherals,telephony devices, calculators, audio/video equipment, voice recordingdevices, etc.). Application of the present technology to such devices,and to UIDs thereof, will be apparent to a person of ordinary skill inthe art upon review of the present disclosure.

FIG. 2 illustrates several example structural interface components(SICs) that may used in UIDs of videogame controllers, in accordancewith embodiments.

FIG. 3 illustrates a perspective view of a videogame controller wherethe directional pad UID 24 and joystick UIDs 20 are shown as removedfrom their coupled positions with respect to the rest of the videogamecontroller. As may be observed, the directional pad UID 24 and joystickUIDs 20 may be mechanically coupled with the videogame controller bybeing inserted within aperture 25 and aperture 21, respectively, and/orinterlocked with one or more locking features accessible from within theapertures (e.g., a snap fit, a twist-lock mechanism, etc.). Further, theUIDs may be electrically and/or communicatively coupled with circuitryof the videogame controller via electrical or electronic featuresaccessible from within aperture 25 and/or aperture 21 (e.g., conductivecontact(s), pin receptacle(s), receiver(s), etc.).

FIG. 4 illustrates a partially exploded view of an example smart UID 100in accordance with one or more embodiments of the present technology. Asshown, a smart user input device (UID) 100 may include a structuralinterface component (SIC) 110 such as joystick 120, and/or a sensormodule component (SMC) 130 including a casing 140, actuation componentry(e.g., rod 150 operably coupled with a bearing (not shown) allowingmovement), a sensor 160 for detecting operation of the smart UID (suchas, for example, movements of the actuation componentry as the SIC 110is maneuvered by a user), and/or a local memory 170 configured to storeinformation (e.g., statistics) about the smart UIDs movements or otherusage characteristics.

As may be observed from FIG. 4, in some embodiments thumbstick 120 maybe detachably mated with rod 150 (e.g., in a snap-fit manner), and rod150 may be coupled with one or more bearing components allowing movementin one or more directions (e.g., pivoting movements, rotationalmovements, etc.) responsive to the way the user maneuvers thumbstick120. Sensor 160 may be operatively coupled to either or both of thethumbstick 120 and/or the actuation componentry, and be configured todetect movements thereof. Local memory 170 may be physically coupledwith one or more components of the smart UID 100, and be configured toreceive, track, and/or store information (e.g., statistics) about thesmart UID 100's movements (or movements of a subpart of the smart UID100) or other usage characteristics about the smart UID 100(collectively referred to herein as “usage information,” or “usage data”or “usage metrics”)

Usage information, as well as other information associated with a smartUID may be stored on the local memory 170. For example, in someembodiments the memory 170 may store statistical information, empiricalinformation about the smart UID of the type to which the memory isassociated, and/or identification information (discussed below), or anyother information, as discussed herein. For instance, the manufacturerof a smart UID 100 may store a value in memory 170 representing the lifeexpectancy of the smart UID or a subpart thereof (e.g., average UIDoperations-to-failure=25,000 individual toggles of to theleft/right/up/down; expected SIC fatigue life=30,000 stress cycles(e.g., 30,000 presses); average revolutions of a wheel type UID beforefailure=100,000 revolutions; etc.).

In some embodiments, the local memory 170 may store machine readableinstructions that, when executed by a processor coupled thereto,compute, estimate, and/or store additional information about the smartUID 100 or a subpart thereof (e.g., total number of presses or togglesto date, number of presses or toggles since a repair event, averagenumber of times pressed or toggled during a gaming session, averagenumber of times pressed or toggled during a certain time period (perday, per week, per year, etc.), proportional use relative to other UIDsof the same controller, or any other pattern of use, etc.).

As shown in FIG. 4, in some embodiments smart UID 100 may include or beconfigured with an visible indicator, such as LED 102, that may be usedto provide a user with a visual indication about the condition of asmart UID 100 or subpart thereof. The visual indication may be operatedor activated based on the information stored in the local memory 170 (orinformation processed in accordance with machine readable instructionsstored thereon). Although only one LED is depicted in FIG. 4, multipleLEDs may be provided for the same smart UID 100 (or subpart thereof).The visual indication may be conveyed by one or more LEDs emitting lightin accordance with one or more of color, a blinking pattern, a number orpattern of total LEDs emitting light at a given time, etc.

For instance, the LED may be configured to emit a green light when thesmart UID 100 or subpart thereof is in good/acceptable condition, ayellow light when the smart UID 100 or subpart thereof is nearing theend of its expected lifetime, and a red light when the smart UID 100 orsubpart thereof is either presently malfunctioning or has been used pastits expected lifetime (in each case based on one or more metrics,thresholds, and/or relationships between usage and lifetime that arestored in local memory 170). In some embodiments, the light emitted fromthe LED 102 may follow a gradient from one color to the next, so thatthe user can qualify the condition of the smart UID 100 or subpartthereof with more precision. For example, the LED 102 may emit a brightgreen light when the smart UID 100 or subpart thereof is brand new andmay gradually fade from bright green to a bright yellow as the smart UID100 or subpart thereof gradually proceeds toward and reaches itsexpected half-life, and then gradually fade from bright yellow to brightred as the smart UID 100 or subpart thereof proceeds toward and reachesthe end of its expected lifetime, for instance.

In another example, the LED may be configured to emit flashes of lightin different patterns associated with different conditions. For example,the LED 102 may emit light constantly when the smart UID 100 or subpartthereof is in good condition (or not beyond a predefined thresholdrelative to an expected lifetime of the smart UID or subpart thereof),and may begin blinking when the smart UID 100 or subpart thereof is inneed of replacement (or beyond a predefined threshold relative to theexpected lifetime of the smart UID or subpart thereof).

In still another example, the smart UID 100 or subpart thereof mayinclude multiple LEDs, and the pattern of LEDs emitting light maycorrespond to the condition of the smart UID 100 or subpart thereof. Forinstance, a smart UID 100 or subpart thereof may include ten LEDs, witheach LED representing 10% of the smart UIDs total remaining life. Abrand new (unused) smart UID with this configuration may emit light fromall ten LEDs—indicating that 100% of the UIDs life is left remaining. Asthe smart UID 100 is used, and usage metrics are stored in local memory170, the LED's may sequentially turn off to indicate the percentage ofremaining life left in the smart UID 100 to the user. For instance, ifthe manufacturer stored in the local memory of a thumbstick styled smartUID a value of 20,000 operations as the expected lifetime metric of thesmart UID 100, and the technology disclosed herein tracked and storedthe usage of the smart UID 100, one LED may turn off with every 2,000operations (10% of 20,000) detected for the particular smart UID). Thus,the user can see clearly the amount of life remaining for its UID. Asnoted, the technology disclosed herein may be applied to a smart UIDdevice as a whole, and/or to individual subparts of the smart UID (e.g.,the SIC 110, the SMC 140, etc.).

It should be appreciated that many other visual indicatorconfigurations, patterns, or indications may be utilized to provide auser with information about the remaining life of a smart UID 100 orsubpart thereof. Indeed, in some instances the visual indicator mayinstead (or in addition) be provided on another part that is distinctfrom and not mechanically coupled to the smart UID 100 or subpartthereof (a charging port, the videogame console, a display or LED on acomputer, a smartphone, a tablet, etc.), and may provide more or lessinformation, or different information, than provided in the foregoingexamples, based on information stored in the memory 170 including usageinformation. All such embodiments are contemplated by and intended tofall within the scope of the present disclosure.

In some embodiments smart UID 100 may include or be configured with anaudible indicator. That is, in some embodiments, the smart UID 100 maybe equipped with or operatively coupled to a speaker, and usageinformation may be provided to a user via the speaker. For example, asmart UID may include an embedded speaker, and a memory coupled with thesmart UID may be configured with machine readable instructions that,when executed by a processor, cause the speaker to audibly announce ausage information about the smart UID (e.g., status, remaining lifeexpectancy in hours/days/percentage, etc.).

As shown, in some embodiments the smart UID 100 may include anidentification component 180. In some instance, the identificationcomponent 180 may be stored in or otherwise accessible to the localmemory 170. For example, the memory 170 may include an identificationcomponent 180 for the smart UID 100 in the form of a read-onlyelectronic identification number or other device identifier (e.g., anelectronic serial number or ID token). In another example, the smart UID100 may include a chip (e.g., a microchip), distinct from the memory170, that may store, provide or otherwise serve as the identificationcomponent 180.

Equipped with its own identification component 180 and memory 170, thesmart UID 100 is capable of providing information about the way oramount with which it has been used to date. This information may formthe basis for an estimated time-to-failure for a given smart UID (orsubpart thereof), and may be used to inform a user of the need for areplacement smart UID before the smart UID fails or otherwisemalfunctions. Moreover, this information may be useful for a buyerlooking to purchase a used replacement smart UID for their controller.The buyer may access the local memory 170 of the smart UID 100 (e.g., byconnecting it) to check the statistical and prior usage historyinformation of the smart UID 100 to determine or confirm the seller'sclaims about the condition and/or history of the smart UID 100's use.Thus, in some embodiments the usage information about a particular smartUID (or subpart thereof) is configured to remain with the smart UIDitself, regardless of whether the smart UID is removed from thevideogame controller, moved to another controller, or whether it tradeshands among users. Accordingly, users can more effectively andaccurately track the usage of their UIDs (or subparts thereof) and takesteps to replace the smart UIDs (or subparts thereof) in advance ofoperation failures.

Although the embodiments depicted in FIG. 4 depicts the sensor 160,memory 170, ID component 180, and LED 102 as being housed/embeddedwithin (or otherwise coupled to/with) the casing 140 of SIC 130, one orordinary skill in the art will appreciate that such components can behoused/embedded within or otherwise coupled to/with any other componentof smart UID 100. That is, the present disclosure should be understoodto contemplate embodiments where one or more of the sensor 160, memory170, ID component 180, and LED 102 are housed/embedded within orotherwise coupled to/with any one or more parts of the SIC 110 (e.g.,thumbstick 120), the SMC 130 (e.g., rod 150, bearing mechanism (notshown), casing 140, etc.).

Moreover, the present disclosure also contemplates embodiments wherethere are several sensor(s) 160, local memory 170, ID component 180and/or LED 102 components, some dedicated to one part of the smart UID100, and others dedicated to other parts of the smart UID 100. Forexample, referring to FIG. 4, the SIC 110 may include its own IDcomponent, memory, and/or sensor, and the SMC 130 may include its own IDcomponent, memory, and/or sensor (separate from the SIC 110's). Thetime-to-failure estimates provided by the technology disclosed hereinmay, for example, indicate that the SMC 130 is ripe for replacement, butthat the SIC 110 has much more life left. Thus, instead of purchasing anentire smart UID 100 apparatus for replacement (including both an SICand an SMC), the user may instead opt only to purchase a replacement SMCif they wish (and simply snap their current SIC onto the new SMC when itarrives). In this manner, the present technology may help inform a useras to what parts actually need to be replaced and which do not, savingcosts and preserving resources.

As shown, smart UID 100 or a subpart thereof may include one or moreconducting pins 190. Conducting pins 190 may be operatively coupled toone or more of sensor 160, local memory 170, and/or identificationcomponent 180, and may provide a coupling link between one or more ofthese components (or other components or circuitry of smart UID 100) andone or more components or circuitry of a videogame controller with whichthe smart UID 100 is used/connected. Conducting pins 190 mayenable/allow a processor of a videogame controller to access and/oroperate on information stored in memory 170. In some embodiments (e.g.,embodiments where the smart UID 100 or subpart thereof does not includeits own microprocessor or microcontroller), signals generated by sensor160 may be interpreted by the videogame controller's processor, and thevideogame controller's processor may thereafter cause data to be writteninto memory 170 that corresponds to usage of the smart UID 100 (e.g.,based on the information received from the sensor, and/or in accordancewith instructions stored on memory 170). In some embodiments, onlycertain information may be accessible to a videogame controllerscomponentry (e.g., its processor), and/or only certain read/writeoperations may be performed by a videogame controller's componentry.That is, in some embodiments the memory 170 may not be entirelyaccessible to a non-local processor, and in other embodiments it may.

Although FIG. 4 depicts a thumbstick styled smart UID 100, it should beappreciated that the present technology extends to and may be applied inany and all types or styles of UID componentry (e.g., directional pads,wheels, triggers, sliders, buttons, toggles, switches, wheels, etc.),including any type of UIDs used in other electronic devices as alreadynoted (e.g., telephony devices, remotes, calculators, etc.)

For instance, FIG. 5 illustrates a partially exploded view of an exampledirectional pad styled smart UID 200, in accordance with one or moreembodiments of the present disclosure. As shown, smart UID 200 mayinclude an SIC 210 such as directional pad 220, and/or an SMC 230including a casing 240, actuation componentry (e.g., tact buttons 250,exposed through an aperture in casing 240 and operably coupled with aninternal control panel such as a printed circuit board), a sensor 260(e.g., which may be the printed circuit board itself, or another sensorydevice) for detecting operation of the smart UID 200 (e.g., detectingwhen the actuation componentry (here, tact buttons 250) is/are engaged),and/or a memory 270 configured to store usage information (e.g.,statistics regarding presses of the tact button 250) about the smart UID200 s operation, and/or other information associated with UID.

As may be observed from FIG. 5, in some embodiments directional pad 220may be removably/detachably fitted within aperture 241 of casing 240 andrest upon or be mated with tact buttons 250. Directional pads may beconfigured to couple with SMCs or videogame controller structures in avariety of ways, and one with ordinary skill in the art will recognizethe present technology may be applied to any such configurations. Somesuch configurations (not shown in detail) may involve a lower edge ofthe directional pad 220 being configured with a lip that extends alongits perimeter and fits into a complementary channel within the SMCcasing 240 (or other structure). In other instances the actuationcomponentry itself, or another structure nearby, may include structuralfeatures that allow complementary features of the directional padstructure to be fitted therewith or snapped thereto. Regardless of theconfiguration, the directional pad 220 is arranged such that, whenpressed by a user in an area over one of the tact buttons, thecorresponding tact button will make physical or electrical contact(directly or indirectly) with a sensor 260 (which in some instances maybe a printed circuit board with a conducting contact that the tactbutton touches when pressed) that operates to actuate a signalresponsive to the way the user maneuvers directional pad 220. Sensor 260may be operatively coupled to either or both of the directional pad 220itself, the casing 240, and/or the actuation componentry (e.g., coupledwith a portion of tact buttons 250), and be configured to detectmovements/operations thereof or changes thereto. Local memory 270 may bephysically coupled with one or more components of the smart UID 200, andbe configured to receive, track, and/or store information (e.g.,statistics) about the smart UID 200's movements (or movements of asubpart of the smart UID 200) or other usage characteristics about thesmart UID 200 (collectively referred to herein as “usage information,”“usage data,” or “usage metrics”).

Usage information, as well as other information associated with a smartUID may be stored on the local memory 270. For example, in someembodiments the local memory 270 may store statistical information,empirical information about smart UIDs of the type to which the localmemory is associated or operatively coupled, and/or identificationinformation (discussed below), or any other information, as discussedherein. For instance, the manufacturer of a smart UID 200 may store avalue in memory 270 representing the life expectancy of the smart UID200 or a subpart thereof (e.g., average UID operations-to-failure=60,000collective presses, whether to the left/right/up/down, expected SICfatigue life=23,000 stress cycles (e.g., 23,000 presses of an individualportion of the directional pad (i.e., 23,000 presses of the leftdirection portion of the directional pad 220), average tact button timeto failure=6 years from first use under low use conditions, 4 years fromfirst use under moderate use conditions, 2 years from first use underhigh/excessive use conditions, etc.).

In some embodiments, the local memory 270 may store machine readableinstructions that, when executed by a processor coupled thereto, computeand/or estimate additional information about the smart UID 200 or asubpart thereof, e.g., total number of presses to date, number ofpresses since a repair event, average number of times pressed during aparticular game or gaming session, average number of times pressedduring a certain time period (e.g., per day, per week, per year, etc.),proportional use relative to other smart UIDs of the same controller(based on any one or more of the foregoing metrics, or other metrics),or any other pattern of use, etc.

As shown in FIG. 5, in some embodiments smart UID 200 may include or beconfigured with an visible indicator, such as LED 202, that may be usedto provide a user with a visual indication about the condition of asmart UID 200 or subpart thereof. The visual indication may be operatedor activated based on the information stored in the memory 270 (orinformation processed in accordance with machine readable instructionsstored thereon). Although only one LED is depicted in FIG. 5, multipleLEDs may be provided for the same smart UID 200 or subpart thereof. Asexplained above with reference to FIG. 4, the visual indication may beconveyed in any manner, including by one or more LEDs emitting light inaccordance with one or more of color, a blinking pattern, a number oftotal LEDs emitting light at a given time, etc., or any combination ofthe foregoing. It should be appreciated that many other visual indicatorconfigurations, patterns, or indications may be utilized to provide auser with information about the remaining life of a smart UID or subpartthereof. Indeed, in some instances the visual indication (e.g., the LED)may instead (or in addition) be provided on another part that isdistinct from and not mechanically coupled to the smart UID (a chargingport, the videogame console, a display or LED on a computer, asmartphone, a tablet, etc.), and may provide any amount of detail thatmay be obtained from the information stored on or determined frominformation stored on local memory 270. All such embodiments arecontemplated by and intended to fall within the scope of the presentdisclosure.

In some embodiments smart UID 200 may include or be configured with anaudible indicator. That is, in some embodiments, smart UID 200 may beequipped with or operatively coupled to a speaker, and usage informationmay be provided to a user via the speaker. For example, a smart UID mayinclude an embedded speaker, and a memory coupled with the smart UID maybe configured with machine readable instructions that, when executed bya processor, cause the speaker to audibly announce a usage informationabout the smart UID (e.g., status, remaining life expectancy inhours/days/percentage, etc.).

As shown, in some embodiments the smart UID 200 may include anidentification component 280. In some instance, the identificationcomponent 280 may be stored in or otherwise accessible to local memory270. For example, the memory 270 may include an identification component280 for the smart UID 200 in the form of a read-only electronicidentification number or other device identifier (e.g., an electronicserial number or ID token). In another example, the smart UID 200 mayinclude a chip (e.g., a microchip), distinct from the memory 270, thatmay store, provide or otherwise serve as the identification component280 (a part identifier).

Equipped with its own identification component 280 and memory 270, thesmart UID 200 (or subpart thereof) is capable of providing informationabout the way or amount with which it has been used to date. In otherwords, with the technology disclosed herein, the history of the smartUIDs usage may be tracked, monitored, maintained, and/or used to assessthe condition of the smart UID. Such information may include or form thebasis for an estimated time-to-failure for a given smart UID (or subpartthereof), and may be used to inform a user of the need for a replacementUID before the smart UID 200 fails or otherwise malfunctions. In anotherexample, this information may be useful for a buyer looking to purchasea replacement smart UID for their controller. The buyer may access thelocal memory 270 of the smart UID 200 being sold to check thestatistical and prior usage history information of the smart UID 200 toconfirm the seller's claims about the condition and/or history of thesmart UID 200's use. As discussed in more detail below, a smart UID maybe coupled with a computing device configured to receive or readinformation from the smart UID's memory and generate a report based onthe information stored therein. The present disclosure provides asolution to meet the need in the market for tracking usage informationabout buttons, paddles, triggers, wheels, dials, thumb sticks,directional pads, etc. of videogame controllers. In particular, in someembodiments the present disclosure provides a way for the usageinformation about a particular smart UID (or subpart thereof) tophysically remain with the smart UID itself, regardless of whether thesmart UID is removed from the videogame controller, moved to anothercontroller, or whether it trades hands among users. Accordingly, userscan more effectively and accurately track the usage of UIDs (or subpartsthereof) and take steps to replace the UIDs (or subparts thereof) inadvance of operation failures.

Although the embodiments depicted in FIG. 5 depicts the sensor 260,local memory 270, ID component 280, and LED 202 as being housed/embeddedwithin (or otherwise coupled to/with) the casing 240 of SIC 230, one orordinary skill in the art will appreciate that such components can behoused/embedded within or otherwise coupled to/with any other componentof smart UID 200. That is, the present disclosure should be understoodto contemplate embodiments where one or more of the sensor 260, localmemory 270, ID component 280, and LED 202 are housed/embedded within orotherwise coupled to/with any one or more parts of the SIC 210 (e.g.,directional pad 120), one or more parts of the SMC 230 (e.g., tactbutton 250, printed circuit board (not shown), casing 240, etc.).

Moreover, the present disclosure also contemplates embodiments wherethere are several sensor(s) 260, memory 270, ID component 280 and/or LED202 components, some dedicated to one part of the smart UID 200, andothers dedicated to other parts of the smart UID 200. For example,referring to FIG. 5, the SIC 210 may include its own ID component,memory, and/or sensor, and the SMC 230 may include its own ID component,memory, and/or sensor (separate from the SIC 210's). The time-to-failureestimates provided by the technology disclosed herein may, for example,indicate that the SMC 230 is ready for replacement, but that the SIC 210has much more life left. Thus, instead of purchasing an entire UIDreplacement (including both an SIC and an SMC), the user may instead optto purchase only a replacement SMC if they wish (and simply snap theircurrent SIC onto the new SMC when it arrives). In this manner, thepresent technology may help inform a user as to what parts actually needto be replaced, and which do not, saving costs and preserving resources.

As shown, smart UID 200 or a subpart thereof may include one or moreconducting pins 290. Conducting pins 190 may be operatively coupled toone or more of sensor 260, local memory 270, and/or identificationcomponent 280, and may provide a coupling link between one or more ofthese components (or other components or circuitry of smart UID 200) andone or more components or circuitry of a videogame controller with whichthe smart UID 200 is used/connected. Conducting pins 290 mayenable/allow a processor of a videogame controller to access and/oroperate on information stored in memory 270. In some embodiments (e.g.,embodiments where the smart UID 200 or subpart thereof does not includeits own microprocessor or microcontroller), signals generated by sensor260 may be interpreted by the videogame controller's processor, and thevideogame controller's processor may thereafter cause data to be writteninto memory 270 that corresponds to usage of the smart UID 200 (e.g.,based on the information received from the sensor, and/or in accordancewith instructions stored on memory 270). In some embodiments, onlycertain information may be accessible to a videogame controllerscomponentry (e.g., its processor), and/or only certain read/writeoperations may be performed by a videogame controller's componentry.That is, in some embodiments the memory 270 may not be entirelyaccessible to a non-local processor, and in other embodiments it may.

In some embodiments, smart UIDs of the present disclosure may becommunicatively coupled with a computing device and/or a display. Thecomputing device may read information from the smart UID's memory, and,upon execution of machine readable instructions effectuating the same,provide a visual indication of the smart UIDs usage and/or remaininglife. In some instances, visual indications for multiple smart UIDsinserted within a videogame controller may be provided on the interface.

FIG. 6 illustrates an example GUI that may be configured, by executingmachine readable instructions stored in a memory operatively coupled toa processor, to provide information (e.g., via visual, graphical,numerical, textual, or animated representation) about one or more smartUIDs of a connected videogame controller. The information may beobtained computed, estimated or determined (via execution of machinereadable instructions) based upon information obtained from the memoriesof the connected smart UIDs, or their subparts, in accordance with oneor more embodiments of the present disclosure. The information, orestimates/computations/determinations based on the information, may beprovided to a computing device or display whereupon the GUI may beprovided. In some embodiments, as shown, the GUI may include detailwindows (or zones) associated with the various smart UIDs of thevideogame controller. The detail windows may include a range ofinformation about a given smart UID, based on the information obtainedfrom the memories of the one or more connected smart UIDs. Thisinformation may include any information about the smart UID, including,by way of example and not by way of limitation: an estimated percentageof life remaining for the given smart UID; an estimated percentage oflife used up for a given smart UID; an estimated real-worldtime-to-failure of a given smart UID based on the usage history for thesmart UID; an estimated calendar date upon which the smart UID isexpected to fail; an estimated date upon which a new UID should beordered; a breakdown of the usage data for individual subparts of thesmart UID (e.g., the SMC, the SIC, etc.); and the like.

Further still, in some embodiments, the presently disclosed systems,devices, and methods may provide: an alert or notification to a user; agraphical representation of the history of the smart UID's usage (e.g.,a detailed dive into patterns of use, forces applied, fatigue cycles,times of peak usage, pressure patterns, etc.); a link or hyperlink to awebsite where the correct replacement part may be ordered; a link orhyperlink to a website with a tutorial or other information about how toremove, install and/or clean the smart UID part of interest; etc.

For example, FIG. 6 illustrates a GUI showing smart UID lifetimeinformation for the smart UIDs associated with a connected videogamecontroller, in accordance with one or more embodiments of the presentdisclosure. As shown, one or more details about each smart UID may beprovided in detail windows associated with the various smart UIDs (here,graphically/visually associated by lines). For example, as shown in GUI300, detail window 301 is associated with and provides information aboutthe life remaining in the left bumper styled smart UID (e.g., the amountof time until the left bumper styled smart UID is expected to fail ormalfunction). As shown, the information is represented as a percentageof total expected life (e.g., 98%), but it may be represented in anymanner, and for any other metric relevant to a smart UIDs condition,including any of themeasures/metrics/determinations/estimates/computations discussed herein.As shown, the information may be conveyed in one or more of a graphical(e.g., symbolic status/progress bar) or numerical/textual manner (e.g.,“75%”).

In some embodiments, as discussed above, a given smart UID may haveseveral subparts or subcomponents for which lifetime information is alsotracked and stored, and, in some instances, of which the smart UID'stotal estimated lifetime is a function. For instance, detail window 304includes information about the directional pad styled smart UID. Adropdown feature 305 (which may be selected by a user) may provideadditional information in zone 306 about the subparts or subcomponentsof the directional pad styled smart UID; here, providing additionalinformation about the left, right, up and down tact buttons thedirectional pad structural component interacts with to actuatefunctionality within the game. The total lifetime measure (or othermetric being measured/provided) of the smart UID may be computed basedon an aggregate measure of the one or more subpart total lifetimemeasures (which may or may not be of the same type of measure ormetric). For example, as shown in FIG. 6 with reference to numerals 304and 305, the directional pad smart UID is shown as having 74% of itstotal expected life remaining. This may be computed based on an averageof the expected life remaining for each of the one or more reportingsubcomponents (e.g., left tact button (75%)+right tact button (72%)+uptact button (76%)+down tact button (73%)/(4)=(74%)). In otherembodiments, a minimum (or any other statistical measure) might becomputed and form the basis for the information conveyed about the smartUID (e.g., the directional pad smart UID showing 72% (minimum) in thecontext of the foregoing example, instead of showing 74% (average)).

In some embodiments, the GUI may provide a selectable link or hyperlinkto a site where the correct replacement part may be ordered for aparticular smart UID, or a link or hyperlink to a site where a tutorialor other information about how to order, remove, repair, install and/orclean the smart UID part of interest; etc. Such a link or hyperlink maybe included within a detail window for a UID. For example, detail window307 associated with the right trigger smart UID includes a hyperlink 308which a user may select to visit a website where a replacement righttrigger smart UID may be purchased. Hyperlinks may be provided for eachsmart UID at all times, or at selective times. For instance, hyperlink308 may only appear in detail window 307 when the expected liferemaining for the right trigger falls beneath a certain threshold (e.g.,when the expected life remaining for the smart UID falls below 25%). Inother examples, any other computation, determination, or triggeringevent may cause machine readable code to be executed such that arelevant hyperlink appears in the GUI displaying information about asmart UID.

In some embodiments, the GUI may provide a selectable icon which mayopen an expanded view or other graphical representation of the historyof the smart UID's usage. For example, the selectable icon 309associated with the right trigger styled smart UID may be selected toopen a window that provides a more a detailed dive into the patterns ofuse (over a specified period of time), the force(s) applied to variousparts of the smart UID, fatigue cycles, times of peak use, pressurepatterns, calendar time and/or date of expected failure, etc.

In embodiments, any number of other selectable icons may be provided viathe GUI to provide information or communication with a user about theinformation. For instance, clock icon 309 may be selected to providemore detailed information about the dates and times of expectedfailures, the suggested last date to place an order for a new UIDcomponent to avoid interruption, etc. In another example,notification/alert icon 311 may be provided when the system generates anotification or alert (e.g., relevant message) for the user. Forinstance, the system of the present disclosure may determine, viaexecution of machine readable instructions, that the left trigger isused substantially less than the right trigger, and may notify the user(when the right trigger falls below a predetermined threshold, forexample) that they may swap the left and right triggers (instead ofbuying an entirely new right trigger smart UID) in order to efficientlyextend the usable life of the smart UIDs as implemented with the givencontroller. Such alerts or notifications, or any of the otherinformation obtained or determined by the systems and methods disclosedherein, may be forwarded or provided to a user via other displays aswell, such as the display of their cellular phone via SMS message.

FIG. 7 illustrates an example system within which the smart UIDtechnology of the present disclosure may be implemented, in accordancewith one or more embodiments of the present disclosure. As shown, system700 may include a display 703, a videogame console 702, and a videogamecontroller 701 including one or more smart UIDs as disclosed herein. Anyone or more of videogame controller 701 (including one or more of thesmart UIDs deployed within the videogame controller 701), the videogameconsole 702, and the display 703 may be communicatively, electrically,and/or mechanically coupled with one another to facilitate the systemsand methods disclosed herein. For example, the circuitry and electroniccomponents included in videogame controller 701 may access the localmemories of one or more of the individual smart UIDs, and/or may processthe information in accordance with machine readable instructions, and/ormay generate signals that may be transmitted to console 702. Thevideogame being run via console 702, or the console 702 (e.g., throughan operating system run by the console), may include the machinereadable instructions that, when executed, provide a GUI on display 703such as GUI 300 illustrated in FIG. 6. The GUI may be in the form of asubframe of a larger GUI, or in some embodiments may be a selectablemenu item a user may select through the game interface.

The components of system 700 are depicted as being communicativelycoupled through one or more wires (e.g., wire 704, 705). However, itshould be noted that wireless communication protocols may also beemployed as desired in the various embodiments of the presentdisclosure. Moreover, although not depicted in this manner, in someembodiments of the present disclosure the display 703, the console 702,the controller 703, and the smart UIDs may all be comprised in a singledevice (e.g., a handheld Nintendo 3DS). Further, any one or more of theforegoing may include or be otherwise deployed with computing modulesand/or technology that enables any one or more of the features and/ortechnologies disclosed herein. FIG. 10 discusses such modules in furtherdetail.

In some embodiments, the user may be prompted (by the game, by thecontroller, or otherwise), to perform a pattern of button presses sothat the system may determine the performance or weakness of any one ormore of the collective parts. For example, the system may suggest (e.g.,via an alert, notification, or otherwise) that the user execute apattern of button, trigger, and or joystick operations that are requiredfor a given game. The user may perform these operations, the signalsgenerated in response thereto may be perceived and compared against amodel or template signal profile for the same pattern, and, based on thecomparison, the system may determine which of the one or more smart UIDsis not working properly such that the functionality desired in the gamecannot be activated, or is not expected to function as consistently asdesired. This type of information may be relevant to an estimatedlifetime of the overall controller (which may have its own local memorystoring the same type of information discussed herein with respect toindividual smart UIDs), and/or may be relevant to a computationperformed for the determination/estimated remaining lifetime of anindividual smart UID.

FIG. 8 illustrates an example method 800 for providing information to auser relevant to a smart UID, in accordance with one or more embodimentsof the present disclosure. As shown, at operation 802, method 800 maydetect a usage of a smart UID. At operation 804, method 800 may storeinformation about the usage of the smart UID in a local memoryassociated with the smart UID. At operation 806, method 800 may estimatethe smart UID's remaining time-to-failure (i.e., remaining life) based,in whole or in part, on: an estimated lifespan for smart UIDs of thattype, the usage measure (which may be accumulated to account for priorusage (e.g., a usage history), and/or the performance of the smart UIDduring a test operation. At operation 808, method 800 may provide one ormore of a graphical representation, a textual indication, an audible orvisual notification or alert conveying information about past usage orcurrent condition of the smart UID. At operation 810, method 800 mayprovide a recommendation to the user based on the estimatedtime-to-failure of the smart UID, the estimated time to failure ofanother smart UID that could be exchanged with the smart UID, and/oranticipated future usage of the smart UID (e.g., recommend to place anorder for a replacement smart UID via a particular website to receivethe replacement UID before the estimated time-to-failure passes).

FIG. 9 illustrates an example method 900 for providing information to auser relevant to a smart UID, in accordance with one or more embodimentsof the present disclosure. As shown, at operation 902, method 900 maydetect a movement of a smart UID. At operation 904, method 900 may storea record of the occurrence of the movement for the smart UID in a memoryassociated with the smart UID. At operation 906, method 900 may computea total usage measure for the smart UID based on the record combinedwith prior movements of the smart UID detected and recorded in thememory associated with the smart UID. At operation 908, method 900 maydetermine an expected time-to-failure (i.e., the remaining life) for thesmart UID based, in whole or in part, on the total usage measure. Atoperation 910, method 900 may provide one or more of a graphicalrepresentation, a textual indication, an audible notification, or visualalert to a user based, in whole or in part, on the most recent usagerecorded, and/or the total usage measure computed.

Although many of the embodiments of the present disclosure have beenshown to include a local memory 160, 260 located onboard the smart UIDhardware, in some embodiments of the present technology the usageinformation/data is instead stored in a memory location of the videogamecontroller itself, with no memory unit being deployed on the smart UID.In such embodiments, in addition to the various types of informationabout smart UID usage that can be stored (as disclosed herein withreference to local memory 160, 260), an additional unit of data may bestored in the videogame controller's memory that links specific smartUID usage information/data to a specific smart UIDs. For instance, aserial number or ID that corresponds to ID 180, 280 may be associatedwith a subset of the usage data stored in the memory such that the usageinformation for one smart UID may be distinguished from that of anothersmart UID. Furthermore, the usage information for a given smart UID maybe uploaded and stored on an external resource (e.g., cloud storage,servers) that may be accessible to any number of registered users. Thus,in embodiments that do not deploy a local memory 160, 260 locally on thesmart UID hardware itself, information about the smart UID maynevertheless be determined by referring to the last uploaded dataassociated with the given smart UID on an external database (e.g., anational database).

Moreover, in some embodiments of the presently disclosed technology, thedetection, tracking, and storage of information related to smart UIDusage may require resources from the processing engine of the videogamecontroller that cause a time delay (i.e., a lag) in other features ofthe videogame controller—especially where the processing engine of thevideogame controller has limited capacity to perform multiple and/oradditional operations simultaneously. For example, detection andtracking of smart UID usage may require a videogame controller'sprocessing engine (e.g., a microcontroller unit, MCU) to executeadditional operations to determine/validate when a usage event hasactually occurred (e.g., when a button has actually been pressed). Thatis, in some embodiments of the disclosed technology, before building thedata packet that gets sent to the console to indicate a button has beenpressed, the videogame controller's processing engine (e.g., an MCU) maybe required to implement one or more additional filtering operations toseparate out mechanical vibrations that are sensed but which are notactual presses of the button (so that all the mechanical vibrations thatget sensed by a sensor don't get counted as multiple presses forpurposes of registering the usage data in a memory).

Performing such additional operations, including filtering operations,requires additional resources from the processing engine (e.g., theMCU), and, depending on the processing speed/capability of the MCU, maycause an interruption, delay, and/or failure with respect to otherfunctions or operations the MCU manages, monitors, and/or controls(e.g., Audio CODEC, memory, Bluetooth IC, packetizing the data sent tothe console (i.e., building the data packet), etc.). Such interruptions,delays, and/or failures may cause an overall lag or dysfunction in theperformance or operation of the videogame controller (e.g., delay theturnaround time between the moment the smart UID is actuated and themoment the data packet is sent to the controller, which in someinstances may entirely miss the delivery window within which the datapacket must be sent). Such a lag or dysfunction is undesirable in thecontext of a gaming environment, or in other environments. Thus, inaccordance with one or more embodiments of the present disclosure, avideogame controller system is provided comprising two or moreprocessing engines (e.g., two or more MCUs), each configured to bededicated to handling certain functionality.

For example, in some embodiments a first MCU may be dedicated toprocessing signals for the smart UIDs, building the data packetscorresponding to those signals and reporting them to the console (e.g.,in real time or near real time). A second MCU may be dedicated togenerating lighting effects, managing the Audio CODEC, performingstatistical analysis, managing the Bluetooth IC or other IC, sensingother events, storing information in a memory (e.g., a serial flash),and any other functionality or operation of the videogame controller.Thus, by deploying at least two processing engines in the videogamecontroller, at least one of which dedicated, in whole or in part, tosmart UID signal processing and packetization, the other MCU(s) may beutilized for the remaining functions or operations.

In some instances the first processing engine may even me more narrowlydedicated to handling signal processing and packetization of a subset ofthe most heavily used UIDs, offloading the remaining processing workloadto the second processing engine. For example, in some embodiments afirst MCU may be dedicated to processing signals for a primary set ofbuttons (smart UIDs in the location of UID 12, 18, 24, and 20 of FIG.1), processing the signals and building the data packets to report backto the console on a real time or near real time basis. A second MCU maythen be dedicated to processing a set of secondary buttons (smart UIDsin the location of UID 14, 22, 16, and 20 of FIG. 1), generatinglighting effects, managing the Audio CODEC, performing statisticalanalysis, managing the Bluetooth IC or other IC, sensing other events,storing information in a memory (e.g., a serial flash).

To further reduce the turnaround time between a UID being actuated andthe data packet being sent (via signal) to the console, dedicatedhardware may be provided between the smart UID and the MCU of thecontroller to filter the signal generated by the UID before it is sentto the MCU for packetization. Such dedicated hardware may include anysuch filtering hardware known in the art.

FIG. 10 illustrates an example computing module that may be used, eitherin the smart UID, the video game controller, or the console of thepresent disclosure to implement various features of the systems andmethods as disclosed herein.

Referring now to FIG. 10, computing module 1200 may represent, forexample, computing or processing capabilities found within desktop,laptop, notebook, gaming consoles, and tablet computers; hand-heldcomputing devices (tablets, PDA's, smart phones, cell phones, palmtops,etc.); wearable computing devices such as smartwatches; mainframes,supercomputers, workstations or servers; or any other type ofspecial-purpose or general-purpose computing devices as may be desirableor appropriate for a given application or environment. Computing module1200 might also represent computing capabilities embedded within orotherwise available to a given device. For instance, a computing modulemight be found in other electronic devices such as, for example, digitalcameras, videogame consoles, gaming controllers, navigation systems,cellular telephones, videogame controllers, portable computing devices,modems, routers, WAPs, terminals and other electronic devices that mightinclude some form of processing capability.

Computing module 1200 might include, for example, one or more processors(e.g., such as processor 175, processor 275, etc.), controllers, controlmodules, or other processing devices, such as a processor 1204.Processor 1204 might be implemented using a general-purpose orspecial-purpose processing engine such as, for example, amicroprocessor, controller, or other control logic. In the illustratedexample, processor 1204 is connected to a bus 1202, although anycommunication medium can be used to facilitate interaction with othercomponents of computing module 1200 or to communicate externally.

Computing module 1200 might also include one or more memory modules,simply referred to herein as main memory 1208. For example, preferablyrandom access memory (RAM) or other dynamic memory, might be used forstoring information and instructions to be executed by processor 1204.Main memory 1208 might also be used for storing temporary variables orother intermediate information during execution of instructions to beexecuted by processor 1204. Computing module 1200 might likewise includea read only memory (“ROM”) or other static storage device coupled to bus1202 for storing static information and instructions for processor 1204.

The computing module 1200 might also include one or more various formsof information storage mechanism 1210, which might include, for example,a media drive 1212 and a storage unit interface 1220. The media drive1212 might include a drive or other mechanism to support fixed orremovable storage media 1214. For example, a hard disk drive, a solidstate drive, a magnetic tape drive, an optical disk drive, a CD, DVD, orBlu-ray drive (R or RW), or other removable or fixed media drive mightbe provided. Accordingly, storage media 1214 might include, for example,a hard disk, a solid state drive, magnetic tape, cartridge, opticaldisk, a CD, DVD, Blu-ray or other fixed or removable medium that is readby, written to or accessed by media drive 1212. As these examplesillustrate, the storage media 1214 can include a computer usable storagemedium having stored therein computer software or data.

In alternative embodiments, information storage mechanism 1210 mightinclude other similar instrumentalities for allowing computer programsor other instructions or data to be loaded into computing module 1200.Such instrumentalities might include, for example, a fixed or removablestorage unit 1222 and an interface 1220. Examples of such storage units1222 and interfaces 1220 can include a program cartridge and cartridgeinterface, a removable memory (for example, a flash memory or otherremovable memory module) and memory slot, a PCMCIA slot and card, andother fixed or removable storage units 1222 and interfaces 1220 thatallow software and data to be transferred from the storage unit 1222 tocomputing module 1200.

Computing module 1200 might also include a communications interface1224. Communications interface 1224 might be used to allow software anddata to be transferred between computing module 1200 and externaldevices. Examples of communications interface 1224 might include a modemor softmodem, a network interface (such as an Ethernet, networkinterface card, WiMedia, IEEE 802.XX or other interface), acommunications port (such as for example, a USB port, IR port, RS232port Bluetooth® interface, or other port), or other communicationsinterface. Software and data transferred via communications interface1224 might typically be carried on signals, which can be electronic,electromagnetic (which includes optical) or other signals capable ofbeing exchanged by a given communications interface 1224. These signalsmight be provided to communications interface 1224 via a channel 1228.This channel 1228 might carry signals and might be implemented using awired or wireless communication medium. Some examples of a channel mightinclude a phone line, a cellular link, an RF link, an optical link, anetwork interface, a local or wide area network, and other wired orwireless communications channels.

In this document, the terms “computer program medium” and “computerusable medium” are used to generally refer to transitory ornon-transitory media such as, for example, memory 1208, storage unit1220, media 1214, and channel 1228. These and other various forms ofcomputer program media or computer usable media may be involved incarrying one or more sequences of one or more instructions to aprocessing device for execution. Such instructions embodied on themedium, are generally referred to as “computer program code” or a“computer program product” (which may be grouped in the form of computerprograms or other groupings). When executed, such instructions mightenable the computing module 1200 to perform features or functions of thepresent application as discussed herein.

Although described above in terms of various example embodiments andimplementations, it should be understood that the various features,aspects and functionality described in one or more of the individualembodiments are not limited in their applicability to the particularembodiment with which they are described, but instead can be applied,alone or in various combinations, to one or more of the otherembodiments of the application, whether or not such embodiments aredescribed and whether or not such features are presented as being a partof a described embodiment. Thus, the breadth and scope of the presentapplication should not be limited by any of the above-described exampleembodiments.

Terms and phrases used in this document, and variations thereof, unlessotherwise expressly stated, should be construed as open ended as opposedto limiting. As examples of the foregoing: the term “including” shouldbe read as meaning “including, without limitation” or the like; the term“example” is used to provide exemplary instances of the item indiscussion, not an exhaustive or limiting list thereof; the terms “a” or“an” should be read as meaning “at least one,” “one or more” or thelike; and adjectives such as “conventional,” “traditional,” “normal,”“standard,” “known” and terms of similar meaning should not be construedas limiting the item described to a given time period or to an itemavailable as of a given time, but instead should be read to encompassconventional, traditional, normal, or standard technologies that may beavailable or known now or at any time in the future.

The presence of broadening words and phrases such as “one or more,” “atleast,” “but not limited to” or other like phrases in some instancesshall not be read to mean that the narrower case is intended or requiredin instances where such broadening phrases may be absent. The use of theterm “module” does not imply that the components or functionalitydescribed or claimed as part of the module are all configured in acommon package. Indeed, any or all of the various components of amodule, whether control logic or other components, can be combined in asingle package or separately maintained and can further be distributedin multiple groupings or packages or across multiple locations.

Additionally, the various embodiments set forth herein are described interms of example block diagrams, flow charts and other illustrations. Aswill become apparent to one of ordinary skill in the art after readingthis document, the illustrated embodiments and their variousalternatives can be implemented without confinement to the illustratedexamples. For example, block diagrams and their accompanying descriptionshould not be construed as mandating a particular architecture orconfiguration.

While various embodiments of the present disclosure have been describedabove, it should be understood that they have been presented by way ofexample only, and not of limitation. Likewise, the various diagrams maydepict an example architectural or other configuration for thedisclosure, which is done to aid in understanding the features andfunctionality that can be included in the disclosure. The disclosure isnot restricted to the illustrated example architectures orconfigurations, but the desired features can be implemented using avariety of alternative architectures and configurations. Indeed, it willbe apparent to one of skill in the art how alternative functional,logical or physical partitioning and configurations can be implementedto implement the desired features of the present disclosure. Also, amultitude of different constituent module names other than thosedepicted herein can be applied to the various partitions. Additionally,with regard to flow diagrams, operational descriptions and methodclaims, the order in which the steps are presented herein shall notmandate that various embodiments be implemented to perform the recitedfunctionality in the same order unless the context dictates otherwise.

We claim:
 1. A control of a handheld video game controller, comprising:a structural interface component to couple to an actuation component;and a sensor module comprising: the actuation component; a sensor todetect actuation of the actuation component in response to movement ofthe structural interface component; a memory configured to storeinformation associated with the detected actuation, wherein theinformation associated with the detected actuation comprises a valuecorresponding to an amount the control has been used over a period oftime, wherein the value is updated over time in response to the sensordetecting actuation; wherein the memory stores information indicating anamount each of a plurality of subcomponents of the control has been usedover a period of time; and a casing to house the sensor and memory. 2.The control of claim 1, wherein the control is to electrically andphysically couple to the handheld video game controller, wherein aprocessor of the handheld video game controller is to receive a signalgenerated by the sensor in response to detecting actuation, and whereinthe processor of the handheld video game controller is to cause data tobe stored in the memory in response to receiving the signal.
 3. Thecontrol of claim 2, further comprising: one or more conducting pins toelectrically couple the control to the handheld video game controllersuch that the handheld video game controller is to cause datacorresponding to usage of the control to be written into the memory. 4.The control of claim 2, wherein the control is removably coupled to thehandheld video game controller.
 5. The control of claim 1, furthercomprising: a light emitting diode configured to provide a visualindication about an expected remaining life of the control using atleast the information stored in the memory.
 6. The control of claim 1,wherein the memory further stores a read-only identifier of the control.7. The control of claim 1, wherein the structural interface component isa directional pad, wherein the actuation component comprises tactbuttons, wherein the directional pad is coupled to the tact buttons suchthat when the directional pad is pressed in an area over one of the tactbuttons, the sensor detects actuation of the tact buttons.
 8. Thecontrol of claim 7, wherein the memory stores information indicating anamount each of the plurality of tact buttons has been actuated over aperiod of time.
 9. The control of claim 1, wherein the memory stores avalue corresponding to a total number of detected actuations of thecontrol over a period of time or a value corresponding to a total numberof remaining actuations of the control before expected failure.
 10. Thecontrol of claim 1, wherein the memory stores a value representing alife expectancy of the user input device or a subcomponent of the userinput device based on a total number of actuations of the control.
 11. Ahandheld video game controller, comprising: a plurality of controlsremovably coupled to the handheld video game controller, each of theplurality of the controls comprising: a structural interface component,wherein the structural interface component is a thumbstick, adirectional pad, a button, a trigger, or a bumper; an actuationcomponent; a sensor to detect actuation of the actuation component inresponse to movement of the structural interface component; and a memoryconfigured to store information associated with the detected actuation,wherein the information associated with the detected actuation comprisesa value corresponding to an amount the control has been used over aperiod of time, wherein the value is updated over time in response tothe sensor detecting actuation; and a casing to house the sensor andmemory; and circuitry configured to access the memory of each of theplurality of controls and obtain the information stored in each of thememories.
 12. The handheld video game controller of claim 11, furthercomprising: a processor, wherein each of the plurality of controls isconfigured to electrically and physically couple to the video gamecontroller, wherein the processor is configured to receive a signalgenerated by the sensor of each of the plurality of controls in responseto detecting actuation, and wherein the processor is configured to causedata to be stored in the memory of the control in response to receivingthe signal.
 13. The handheld video game controller of claim 11, whereinthe value corresponds to a total number of detected actuations of thecontrol over a period of time or a total number of remaining actuationsof the control before expected failure.
 14. The handheld video gamecontroller of claim 11, wherein the plurality of controls removablycoupled to the handheld video game controller comprise a first controland a second control, the structural interface component of the firstcontrol being different from the structural interface component of thesecond control, wherein the memory of each of the plurality of controlsstores a read-only identifier of the control that differs from thestored read-only identifiers of the other controls.
 15. A non-transitorycomputer-readable medium having executable instructions stored thereonthat, when executed by a processor, cause the processor to performoperations of: retrieving, from a memory of each of a plurality ofcontrols of a handheld video game controller, a stored record of theoccurrence of movement of the control, wherein each of the plurality ofcontrols is removably coupled to the handheld video game controller,wherein each of the plurality of controls comprises a structuralinterface component that is a thumbstick, a directional pad, a button, atrigger, or a bumper; computing a total usage measure for each of theplurality of controls using at least the stored record retrieved fromthe memory of the control; determining an expected life of each of theplurality of controls using at least the total usage measure computedfor the control; and presenting, via a gaming console communicativelycoupled to the handheld video game controller, a graphical userinterface to a user, the graphical user interface displaying a visualrepresentation of the determined expected life of each of the pluralityof controls.
 16. A control of a handheld video game controller,comprising: a structural interface component to couple to an actuationcomponent, wherein the structural interface component is a thumbstick, adirectional pad, a button, a trigger, or a bumper; and a sensor modulecomprising: the actuation component; a sensor to detect actuation of theactuation component in response to movement of the structural interfacecomponent; a memory configured to store information associated with thedetected actuation, wherein the information associated with the detectedactuation comprises a value corresponding to an amount the control hasbeen used over a period of time, wherein the value is updated over timein response to the sensor detecting actuation; and a casing to house thesensor and memory, wherein the memory stores machine readableinstructions that, when executed by a processor coupled thereto,computes one or more of the following parameters: a total number oftimes the control was pressed since a repair event, an average number oftimes the control was pressed during a particular game or gamingsession, and a proportional use of the control relative to othercontrols of the handheld video game controller.